Skip to content

Conversation

@kartiksirigeri
Copy link

@kartiksirigeri kartiksirigeri commented Dec 30, 2025

Proxy handler does not remove the stateful EJB3 from the liveregistry on invocation of @remove annotated method. Check is added to identify invocation of @remove annotated method of stateful EJB3.
Defect link : https://issues.apache.org/jira/browse/TOMEE-4560

@rzo1 rzo1 requested review from dblevins and struberg December 30, 2025 16:10
@kartiksirigeri
Copy link
Author

the build for the pull request failed with, 'Error: This request has been automatically failed because it uses a deprecated version of actions/cache: v2. Please update your workflow to use v3/v4 of actions/cache to avoid interruptions. Learn more: https://github.blog/changelog/2024-12-05-notice-of-upcoming-releases-and-breaking-changes-for-github-actions/#actions-cache-v1-v2-and-actions-toolkit-cache-package-closing-down'...

I do not understand this error.

@rzo1
Copy link
Contributor

rzo1 commented Jan 5, 2026

Thanks for the PR. Please note: https://tomee.apache.org/tomee-8.0-eol.html

The branch uses an EOL GitHub Action version. For that reason the build fails right now.

@kartiksirigeri
Copy link
Author

Thanks for the PR. Please note: https://tomee.apache.org/tomee-8.0-eol.html

The branch uses an EOL GitHub Action version. For that reason the build fails right now.

https://tomee.apache.org/tomee-8.0-eol.html says 'bugs affecting only the tomee-8.x branch will not be addressed' , I am not sure if the issue is only for 8.x as I have been using only this version

@rzo1
Copy link
Contributor

rzo1 commented Jan 5, 2026

Yes, it is very likely that this is also present in newer TomEE versions, as the class itself did not change apart from the javaxjakarta migration. What I meant with the eol notice is that it’s unlikely we’ll do another TomEE 8 release. However, since the issue appears to affect newer TomEE versions as well, we can address it there.

Could we add a unit test to verify the change and reproduce the issue in the first place? From what I can see in the Jira ticket, reproduction code was already provided, so it should be possible to turn that into a unit test.

@kartiksirigeri
Copy link
Author

kartiksirigeri commented Jan 5, 2026

provided

managed to add a unit test case, hope that helps, this test should fail now without the fix...

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants